Dynamic variables

Flows can use all variables available to AI Agents, as described in section Variables.

Turn data

The “turn data” section is different for Flows and contains the following variables:

• user_utterance – last user utterance
• user_utterance_count – sequential number of user utterance in the current conversation node; 1 is the first user utterance, 2 is the second, and so on. This counter resets only when the flow moves to a different conversation node; it is not reset when the flow leaves the node to a non-conversation node – such as a logical condition or extract variables node – and then returns to the same conversation node. The same applies to a conversation node with Skip response enabled: because such a node never waits for user input, passing through it and back to the same conversation node does not reset the count.
• duration – duration of current conversation in seconds
• turns_count – total number of turns in the conversation (across all nodes)
• transitions_count – total number of transitions in the conversation
• visits_count – number of times the current conversation node has been visited in the current conversation; can be used to handle loops in the flow state machine.

Time and date variables

Flows provide their own set of time and date variables, which differ from the Agent's time and date variables. The Agent's variables are returned as formatted text – convenient for embedding in a prompt – whereas Flows additionally expose the individual date and time components as numbers (hour, minute, day of month, month, year, and so on). This gives you finer control and makes logical conditions and Calculate statements much simpler to write, because you can compare numeric values directly instead of parsing a formatted string.

The following time and date variables can be used in Conversation, Logical condition, and Calculate nodes:

Variable	Type	Example value
current_time	str	"15:07:12"
current_date	str	"2025-12-27"
current_datetime	str	"2025-12-27 15:07:12, Sunday"
current_day	str	"Sunday"
current_hour	int	15
current_minute	int	7
current_second	int	12
current_weekday	int	0 (0=Sunday)
current_day_of_month	int	27
current_month	int	12
current_year	int	2025

For example, you can use them in a Logical condition node to implement time-based routing:

Transitions:
  current_hour < 13   --> transition to node A
  Else                --> transition to node B

Use the timezone variable in Flow settings to configure the timezone if needed, for example:

timezone = Europe/Paris